
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
	"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
	<meta http-equiv="content-type" content="text/html; charset=utf-8">
	<title>JsDoc: DeliveryMode</title>
	<style type="text/css">
		body { background-color: #FFFFFF; }
		.TableHeadingColor { background: #CCCCFF; }
		.TableSubHeadingColor { background: #EEEEFF; }
		.TableRowColor { background: #FFFFFF; }
		
		.FrameTitleFont
		{
			font-size: 10pts;
			font-family: Helvetica, Arial, san-serif;
		}
		
		.FrameHeadingFont
		{
			font-size: 10pts;
			font-family: Helvetica, Arial, san-serif;
		}
		
		.FrameItemFont
		{
			font-size: 10pts;
			font-family: Helvetica, Arial, san-serif;
		}
		
		.NavBar
		{
			font-family: Arial, Helvetica, sans-serif;
			background-color: #FFFFFF;
		}
		
		.jsdoc_ctime
		{
			font-family: Arial, Helvetica, sans-serif;
			font-size: 9pt;
			text-align: right;
		}
	</style>
</head>

<body>

<table style="width: 100%">
<tr>
<td class="NavBar" valign="top"><font size="-2">SUMMARY:&nbsp;<a href="#field_summary">FIELD</a>&nbsp;|&nbsp;<a href="#constructor_summary">CONSTR</a>&nbsp;|&nbsp;<a href="#method_summary">METHOD</a></font></td>
<td class="NavBar" valign="top"><font size="-2">DETAIL:&nbsp;<a href="#field_detail">FIELD</a>&nbsp;|&nbsp;<a href="#constructor_detail">CONSTR</a>&nbsp;|&nbsp;<a href="#method_detail">METHOD</a></font></td>
</tr>
</table>

<hr>

<h2>Class DeliveryMode</h2>



<p>
The delivery modes supported by the JMS API are <CODE>PERSISTENT</CODE> and<CODE>NON_PERSISTENT</CODE>.<P>A client marks a message as persistent if it feels that the application will have problems if the message is lost in transit.A client marks a message as non-persistent if an occasionallost message is tolerable. Clients use delivery mode to tell aJMS provider how to balance message transport reliability with throughput.<P>Delivery mode covers only the transport of the message to its destination. Retention of a message at the destination untilits receipt is acknowledged is not guaranteed by a <CODE>PERSISTENT</CODE> delivery mode. Clients should assume that message retention policies are set administratively. Message retention policygoverns the reliability of message delivery from destinationto message consumer. For example, if a client's message storage space is exhausted, some messages may be dropped in accordance with a site-specific message retention policy.<P>A message is guaranteed to be delivered once and only onceby a JMS provider if the delivery mode of the message is <CODE>PERSISTENT</CODE> and if the destination has a sufficient message retention policy.</p>




<hr>

<!-- =========== FIELD SUMMARY =========== -->

<a name="field_summary"> </a> 
<table border="1" cellpadding="3" cellspacing="0" width="100%">
	<tr bgcolor="#CCCCFF" class="TableHeadingColor">
		<td colspan=2>
			<font size="+2"> <b>Field Summary</b></font>
		</td>
	</tr>
	
		<tr bgcolor="white" class="TableRowColor">
			<td align="right" valign="top" width="1%">
				<font size="-1"><code>int</code></font>
			</td>
			<td>
				<code><b><a href="#NON_PERSISTENT">NON_PERSISTENT</a></b></code> 
				<br>
				&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Returns a message for the cause of the exception
			</td>
		</tr>
	
		<tr bgcolor="white" class="TableRowColor">
			<td align="right" valign="top" width="1%">
				<font size="-1"><code>int</code></font>
			</td>
			<td>
				<code><b><a href="#PERSISTENT">PERSISTENT</a></b></code> 
				<br>
				&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Returns a message for the cause of the exception
			</td>
		</tr>
	
</table>
&nbsp;

<!-- =========== END FIELD SUMMARY =========== -->


<!-- ======== CONSTRUCTOR SUMMARY ======== -->
<a name="constructor_summary"> </a>
<table border="1" cellpadding="3" cellspacing="0" width="100%">
<tr bgcolor="#CCCCFF" class="TableHeadingColor">
	<td colspan=2><font size="+2"><b>Constructor Summary</b></font></td>
</tr>

	<tr bgcolor="white" class="TableRowColor">
	   <td>
	
		<code>
		<b><a href="#DeliveryMode">DeliveryMode</a></b>()
		</code>
		  <br>
		  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
		  
The delivery modes supported by the JMS API are <CODE>PERSISTENT</CODE> and<CODE>NON_PERSISTENT</CODE>.
		  </td>
	</tr>

</table>
&nbsp;
<!-- ======== END CONSTRUCTOR SUMMARY ======== -->


<!-- ========== METHOD SUMMARY =========== -->

<!-- ========== EVENT SUMMARY =========== -->



<!-- ========== INHERITED METHODS SUMMARY =========== -->

<br/>

<!-- ========== END INHERITED METHODS SUMMARY =========== -->

<!-- ============ FIELD DETAIL START ========= -->

<a name="field_detail"> </a> 
<table border="1" cellpadding="3" cellspacing="0" width="100%">
	<tr bgcolor="#CCCCFF" class="TableHeadingColor">
		<td colspan=1>
			<font size="+2"> <b>Field Detail</b></font> 
		</td>
	</tr>
</table>


	<!-- One single method detail entry -->
	<a name="NON_PERSISTENT">
	<!-- -->
	</a> <h3>NON_PERSISTENT</h3>
		<pre>int <b>NON_PERSISTENT</b></pre> 
	<ul>
		Returns a message for the cause of the exception
	</ul>
	<hr>

	<!-- One single method detail entry -->
	<a name="PERSISTENT">
	<!-- -->
	</a> <h3>PERSISTENT</h3>
		<pre>int <b>PERSISTENT</b></pre> 
	<ul>
		Returns a message for the cause of the exception
	</ul>
	<hr>


<!-- ============ FIELD DETAIL END ========== -->


<!-- ========= CONSTRUCTOR DETAIL START ======== -->
<a name="constructor_detail"> </a>
<table border="1" cellpadding="3" cellspacing="0" width="100%">
   <tr bgcolor="#CCCCFF" class="TableHeadingColor">
      <td colspan=1>
      <font size="+2"><b>Constructor Detail</b></font>
      </td>
   </tr>

</table>

<a name="DeliveryMode"> </a>
<h3>DeliveryMode</h3>

	<pre><b>DeliveryMode</b>()</pre>
	<ul>
	   
The delivery modes supported by the JMS API are <CODE>PERSISTENT</CODE> and<CODE>NON_PERSISTENT</CODE>.<P>A client marks a message as persistent if it feels that the application will have problems if the message is lost in transit.A client marks a message as non-persistent if an occasionallost message is tolerable. Clients use delivery mode to tell aJMS provider how to balance message transport reliability with throughput.<P>Delivery mode covers only the transport of the message to its destination. Retention of a message at the destination untilits receipt is acknowledged is not guaranteed by a <CODE>PERSISTENT</CODE> delivery mode. Clients should assume that message retention policies are set administratively. Message retention policygoverns the reliability of message delivery from destinationto message consumer. For example, if a client's message storage space is exhausted, some messages may be dropped in accordance with a site-specific message retention policy.<P>A message is guaranteed to be delivered once and only onceby a JMS provider if the delivery mode of the message is <CODE>PERSISTENT</CODE> and if the destination has a sufficient message retention policy.
	</ul>
	
	<!-- PARAMETERS START -->
	
	<!-- PARAMETERS END -->

<hr/>
<!-- END ADDITIONAL ATTRIBUTES  -->
<!-- ========= CONSTRUCTOR DETAIL END ======== -->


<!-- ============ METHOD DETAIL START ======= -->

<!-- ============ METHOD DETAIL END ========== -->



<!-- ============ EVENT DETAIL START ======= -->



<!-- ============ EVENT DETAIL END ========== -->
<div class="jsdoc_ctime">Documentation generated by <a href="http://jsdoctoolkit.org/" target="_parent">JsDoc Toolkit</a> 1.3.3 on Tue Aug 23 2011 02:47:05 GMT-0700 (PDT)</div>
</body>
</html>